perm filename NETDOC.PLN[ESS,JMC] blob sn#020481 filedate 1973-01-13 generic text, type C, neo UTF8
COMMENT ⊗   VALID 00002 PAGES
C REC  PAGE   DESCRIPTION
C00001 00001
C00002 00002	PLAN FOR KEEPING DOCUMENTS IN THE NETWORK
C00009 ENDMK
C⊗;
PLAN FOR KEEPING DOCUMENTS IN THE NETWORK


	At the ARPA IPT principal investigators' meeting, 8-10 January,
John McCarthy was charged with preparing proposals concerning keeping
documents in the network.  As I see it, the issues include the following,
most of which were raised by various people at the IPT meeting and at
the meeting a year ago.

	1. It now costs no more to store a book on either of the terabit
files than to keep it on a shelf.  Therefore, the storage technology is
now adequate to move towards having all the world's literature in a
computer accessible form.  It costs about $5.00 per month marginal cost
to store one more book on the IBM 3330 at the Stanford AI Lab.  The
display terminal situation is not quite so favorable, but many of the
labs are acquiring systems usable for reading.

	2. It should be possible to identify Defense Department needs for
on-line document storage and reading.  It was said at the meeting that
some part of the DoD had RFPed a system for keeping the technical manuals
for obsolete equipment on-line.  It is very important to do all this
in a uniform way so that the eventual goal that all literature be accessible
from everywhere be achieved.  Otherwise, a situation might arise where a
part of the Armed Services will need more than one system of display
consoles because they subscribe to two incompatible information systems.

	3. A prototype of such a standard system can be an ARPA network
system provided we pay due attention to generality.  Already, when files
are transferred between sites on the net various troubles occur.  Here are
some of them.
	a. ASCII made a minor change some years ago, and Stanford has the
old characters and M.I.T. the new.
	b. Different filler characters are used.
	c. The low order bit is treated differently.
	d. Stanford has an extended character set.
	e. NLS text files require a specific hierarchical structure not
used by anyone else.
	These are only the incompatibilities that have accidentally come
to my attention.  Those who use IBM machines have different problems, and
because different balls are used on Selectrics, the IBM users have a
tendency to use the same character codes for different characters in
different situations.

	4. One problem is that of extending the character set beyond that
the 96 charact↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T↓T